In SAS^® Enterprise Miner™, the Interactive Grouping node supports mixed-type data and special user defined coded holdout values. You determine these special codes, or holdout values, based on the business situation. These codes are included in a SAS data set, which SAS calls a Special Codes data set. Each row in the Special Codes data set contains a special code or holdout value that maps to a special missing value. After the Special Codes data set is created, you implement the mapping by setting the Use Special Codes property to Yes, and, by selecting the data set using the Special Codes Data Set property.

If you use a Special Codes data set that includes an interval value which is less than or equal to the value of the Number of Bins property, dupliclate bins in the Interactive window will result. As a result, the score code and the associated labels will be incorrect.

For example, if the Number of Bins property is set to 20, any value from 0-20 in a Special Codes data set will result in that interval value being used in duplicate bins, and very likely in different groups as well. The scorecard generated score code will have an appearance that is similar to the following:

*------------------------------------------------------------*;
* Variable: input;
*------------------------------------------------------------*;
if MISSING(input) then do;
SCORECARD_POINTS = SCORECARD_POINTS + 192;
SCR_input = 192;
end;
else if NOT MISSING(input) AND input <  28 then do;
SCORECARD_POINTS = SCORECARD_POINTS + 162;
SCR_input = 162;
end;
else if NOT MISSING(input) AND input <  39 then do;
SCORECARD_POINTS = SCORECARD_POINTS + 181;
SCR_input = 181;
end;
...

The line "else if NOT MISSING(input) AND input < 39 then do;" is missing a lower bound on the input variable comparison.

The workaround is to set the Number of Bins property value to a value less than all values in the special codes data set.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Enterprise Miner 5.3 is available at:

A fix for this issue for SAS Credit Scoring for Enterprise Miner 5.3 is available at: